You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The uuid package has been bumped from v8 to v11. uuid v11 introduced significant changes in how the package is exported (shifting towards ESM) and changed the binary path from dist/bin/uuid to dist/esm/bin/uuid. If the legacy TypeScript CLI (src/) or any build scripts rely on the CLI binary path of uuid or expect CJS defaults without proper interop, this will cause runtime failures or build breakages.
The update to @snyk/code-client introduces a strict engine requirement for Node.js node: >=20.17.0 and npm: ^11.12.1. While the root package.json allows node: ^22 || ^24, this change effectively drops support for earlier sub-versions of Node 20 (e.g., 20.10.0) which are still commonly used in enterprise CI environments. This will cause installation failures with --engine-strict (which the ps1 script implies is used via .npmrc).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
Where should the reviewer start?
How should this be manually tested?
npm cimake buildsucceedWhat's the product update that needs to be communicated to CLI users?
Fix for CVE-2026-41907 (medium vulnerability)
What are the relevant tickets?
CLI-1504